@aepfli do you think it makes more sense to simply add metadata to the existing gherkin suite? We already have error flags there - we could add metadata to some of the existing flags and error flags, and them update the in-memory providers to support this.

@aepfli do you think it makes more sense to simply add metadata to the existing gherkin suite? We already have error flags there - we could add metadata to some of the existing flags and error flags, and them update the in-memory providers to support this.

I am not sure if integration into the existing suite is suitable. We could enhance the existing ones, with a description of what the purpose of those flags is. But generally i prefer a flagname which already tells me what i can expect from this flag.

This also brings me to the next topic. As we are currently generating the data in each sdk on our own, it might be worth to add a json here with the testdata, which we load into the inmemory provider, wdt?

This also brings me to the next topic. As we are currently generating the data in each sdk on our own, it might be worth to add a json here with the testdata, which we load into the inmemory provider, wdt?

Most in-memory providers can't actually load JSON, so I'm not sure how valuable that would be.

This also brings me to the next topic. As we are currently generating the data in each sdk on our own, it might be worth to add a json here with the testdata, which we load into the inmemory provider, wdt?

Most in-memory providers can't actually load JSON, so I'm not sure how valuable that would be.

i would not load them automagically, but within the tests, we can load the json files, and provide the data as parameter to the inmemory provider. We would centralize the test flag data, and with new gherkin files, which only add new data for experimentation everything should work ootb.

data = loadJsonData(jsonfile)
provider = InMemoryProvider(data) // simple prosa

This also brings me to the next topic. As we are currently generating the data in each sdk on our own, it might be worth to add a json here with the testdata, which we load into the inmemory provider, wdt?

Most in-memory providers can't actually load JSON, so I'm not sure how valuable that would be.

i would not load them automagically, but within the tests, we can load the json files, and provide the data as parameter to the inmemory provider. We would centralize the test flag data, and with new gherkin files, which only add new data for experimentation everything should work ootb.

data = loadJsonData(jsonfile)
provider = InMemoryProvider(data) // simple prosa

Oh, so all implementations would write a simple function loadJsonData or similar which would do the conversion? I guess that's not a bad idea since it might be fairly future-proof when new things are added.

Oh, so all implementations would write a simple function loadJsonData or similar which would do the conversion? I guess that's not a bad idea since it might be fairly future-proof when new things are added.

excactly, and this way we ensure, everyone gets the same data afterall

Merging this at just 2 green checks because it's just some test data and doesn't represent any fundamental new features or changes.